Multiple interface support

ABSTRACT

Aspects describe multiple interface support that provides dynamic switching between new and old interface revisions. A first interface application is selected from a set of alternative interface applications for an industrial automation system. Support for each interface application included in the set of alternative interface applications is provided. A second interface application is downloaded and associated with the first interface application. The second interface application is enabled during runtime. If needed, the second interface application can be selectively disabled and an operation resumed with the first interface application.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of U.S. patent application Ser. No.12/893,550, entitled “MULTIPLE INTERFACE SUPPORT,” filed on Sep. 29,2010, which is a Continuation-in-Part of U.S. patent application Ser.No. 11/536,715, now U.S. Pat. No. 7,856,279 issued Dec. 21, 2010,entitled “MODULE STRUCTURE AND USE FOR INDUSTRIAL CONTROL SYSTEMS,”filed on Sep. 29, 2006; a Continuation-in-Part of U.S. patentapplication Ser. No. 11/536,746, now U.S. Pat. No. 7,835,805 issued Nov.16, 2010, entitled “HMI VIEWS OF MODULES FOR INDUSTRIAL CONTROLSYSTEMS,” filed on Sep. 29, 2006; a Continuation-in-Part of U.S. patentapplication Ser. No. 11/536,760, now U.S. Pat. No. 7,912,560 issued Mar.22, 2011, entitled “MODULE AND CONTROLLER OPERATION FOR INDUSTRIALCONTROL SYSTEMS,” filed on Sep. 29, 2006; a Continuation-in-Part of U.S.patent application Ser. No. 11/536,791, entitled “MODULE CLASSIFICATIONAND SEARCHING FOR INDUSTRIAL CONTROL SYSTEMS,” filed on Sep. 29, 2006; aContinuation-in-Part of U.S. patent application Ser. No. 12/241,319,entitled “MODULE AND HOST MATCHING,” filed on Sep. 30, 2008; aContinuation-in-Part of U.S. patent application Ser. No. 12/241,327, nowU.S. Pat. No. 8,265,775 issued Sep. 11, 2012, entitled “MODULEPUBLICATION AND DISCOVERY,” filed on Sep. 30, 2008; and aContinuation-in-Part of U.S. patent application Ser. No. 12/241,342, nowU.S. Pat. No. 8,041,435 issued Oct. 18, 2011, entitled “MODULE DYNAMICHOSTING,” filed on Sep. 30, 2008, the entireties of which areincorporated herein by reference.

TECHNICAL FIELD

The subject disclosure relates generally to industrial control systemsand more particularly to modular automation within industrial controlsystems.

BACKGROUND

Industrial control systems can employ complex mechanical, electronic,electro-mechanical, and/or robotic machinery to perform variousautomated mechanical and/or electrical functions. Examples of machineryinclude industrial motors, pumps, conveyors, escalators, drills,refrigeration systems, and so forth. An industrial control system canutilize one or more control devices to activate or deactivate themachinery and/or to determine an appropriate level of activation for themachinery (e.g., an amount of current to supply to a variable inputmotor). Additionally, the control devices can be associated with logicalprogram code that determines an appropriate time, degree, manner, andother criteria for operation of the machinery. For example, thedetermination can be based on various circumstances, including an outputof another device, a reading of an optical sensor, an electronicmeasurement, a movement, a number of rotations of a device, and so on.

The machinery can be controlled by at least one industrial controller,such as, for example, programmable logic controllers. The industrialcontrollers can also communicate with higher level computing systems orservers that aggregate data from the controllers and help to manageday-to-day activities of an enterprise. As systems have become morecomplex, however, communications and functional cooperation betweencomponents of the industrial automation system has become a challenge.For instance, when users purchase multiple products from one or morevendors, there is often limited interoperability and consistency betweensuch products. Software and control engineers must then learn eachproduct and how the components interact with each other. Limited productand component consistency suggest that techniques engineers learn forone product do not necessarily carry over to other implementations.

Often, integration of products in the industrial automation system iscomplex and difficult to manage. Process and control engineers cannoteasily code and configure their respective components without concernfor other system components, which may have different manufacturers anddifferent platforms.

Another problem with integration of products is that process and controlengineers focus on underlying technical details, includingimplementation and glue logic, rather than the application levelconcerns, for example process information. For instance, an engineer maydecide to automate a manual section of their plant. The design may startat a high level but soon becomes a series of discussions regardingnonfunctional requirements e.g., distributed component object model(DCOM), transmission control protocol (TCP), transaction rates, and thelike. While these nonfunctional requirements are important, the designof functional requirements is where the true value is to the designer orend user. Thus, the engineer would prefer to focus on functionalrequirements (equipment control, product flow control, and so forth)providing direct improvements in value rather than dealing withsuperfluous technology issues.

In another case, system design does not sufficiently enable trade-offsbetween overhead burden (memory footprint, CPU (central processing unit)cycles, and so forth) and application coupling. For instance, processingload should be distributed across the system in accordance with systemcapabilities. Thus, if one part of the system is shut down, alternativeprocessing capability should be in place to allow production tocontinue. For example, control and process engineers can initiallydesign and install a control system suiting their immediate needs.Current solutions however do not facilitate a smooth and uncomplicatedtransition for the respective changes. Multiple technologies underneathmany vendors' products complicate configuration and management ofsystems. This is also aggravated when third party systems are involved.Such complexity hinders the system's capacity to provide higher-levelinformation and can reduce the ability to configure such systems.

SUMMARY

The following presents a simplified summary in order to provide a basicunderstanding of some aspects of the subject disclosure. This summary isnot an extensive overview and it is not intended to identify key orcritical elements of all aspects nor delineate the scope of any or allaspects. The sole purpose of this summary is to present some concepts ofone or more aspects in a simplified form as a prelude to the moredetailed description that is presented later.

An aspect relates to a device comprising an interface component thatobtains a set of alternative interface applications for an industrialautomation system. The device also comprises a deployment component thatenables a first interface application from the set of alternativeinterface applications. The interface component can maintain support foreach interface application included in the set of alternative interfaceapplications, wherein each interface application is a differentinterface version.

Another aspect relates to a method comprising receiving a firstinterface application and deploying the first interface application.Method also comprises obtaining a second interface application andmapping the second interface application to the first interfaceapplication. Further, method comprises enabling the second interfaceapplication and selectively resuming operation with the first interfaceapplication.

Another aspect relates to a system comprising an interface componentthat retains information related to a first interface application and asecond interface application. System also comprises a mapping componentthat associates the first interface application with the secondinterface application and a validation component that accesses datarelated to a third interface application. Also included in system is adownload component that selectively obtains the third interfaceapplication. The mapping component associates the third interfaceapplication with the second interface application. System also comprisesa deployment component that enables the third interface application andmaintains support for the first interface application and the secondinterface application.

To the accomplishment of the foregoing and related ends, one or moreaspects comprise features hereinafter fully described. The followingdescription and annexed drawings set forth in detail certainillustrative features of one or more aspects. These features areindicative, however, of but a few of various ways in which principles ofvarious aspects may be employed. Other advantages and novel featureswill become apparent from the following detailed description whenconsidered in conjunction with the drawings and the disclosed aspectsare intended to include all such aspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating interaction of a service and ahost in an industrial automation system.

FIG. 2 is a block diagram illustrating a system that utilizes servicesand hosts.

FIG. 3 is a block diagram illustrating a system for matching servicesand hosts.

FIG. 4 illustrates an example industrial control system that supportsmultiple platform configurations, according to an aspect.

FIG. 5 illustrates a schematic representation of an example group ofalternative platform configurations, according to an aspect.

FIG. 6 illustrates an industrial control system that is configured tosupport multiple interfaces and/or multiple interface versions atrun-time, according to an aspect.

FIG. 7 illustrates a schematic representation of a system that isconfigured to provide multiple interface support, according to anaspect.

FIG. 8 illustrates a method for dynamically switching between multipleinterface applications, according to an aspect.

FIG. 9 illustrates a block diagram of a computer operable to execute thedisclosed aspects.

FIG. 10 illustrates a schematic block diagram of an exemplary computingenvironment, according to an aspect.

DETAILED DESCRIPTION

Various aspects are now described with reference to the drawings. In thefollowing description, for purposes of explanation, numerous specificdetails are set forth in order to provide a thorough understanding ofone or more aspects. It may be evident, however, that such aspect(s) maybe practiced without these specific details. In other instances,well-known structures and devices are shown in block diagram form inorder to facilitate describing these aspects.

As used in this application, the terms “component,” “module,” “object”,“service,” “system,” “interface,” or the like are generally intended torefer to a computer-related entity, either hardware, a combination ofhardware and software, software, or software in execution. For example,a component can be, but is not limited to being, a process running on aprocessor, a processor, a hard disk drive, multiple storage drive (ofoptical and/or magnetic storage medium), an object, an executable, athread of execution, a program, and/or a computer. By way ofillustration, both an application running on a controller and thecontroller can be a component. One or more components can reside withina process and/or thread of execution and a component can be localized onone computer and/or distributed between two or more computers. Asanother example, an interface can include I/O components as well asassociated processor, application, and/or API components.

Referring initially to FIG. 1, illustrated is an example industrialautomation system 100, according to an aspect. The industrial automationsystem 100 is configured to utilize modular automation to constructapplications with reusable software that exposes functionality ofcomponents of the industrial automation system 100, while providing anabstraction from details of communication and interaction with suchcomponents.

The industrial automation system 100 includes a host 102 that isconfigured to interface with a user and/or entities (e.g., the Internet,another system, a computer, and so forth), hereinafter referred to asuser 104. The interface between host 102 and user 104 can be throughvarious interface mechanisms, including a human machine interface (HMI)or a graphical user interface (GUI). Although only a single host 102 isillustrated, industrial automation system 100 can include two or morehosts, according to an aspect. According to some aspects, the host 102can be one or more industrial controllers (e.g., programmable automationcontroller (PAC), programmable logic controller (PLC), and so forth).The one or more industrial controllers can be associated with one ormore human machine interfaces (HMIs). The term “industrial controller”as utilized herein can include functionality that can be shared acrossmultiple components or networks.

The host 102 need not be limited to an industrial controller. Accordingto some aspects, the host 102 can be (or can be associated with) one ormore computer or network components within the industrial automationsystem 100. For example, the host 102 can be a computer, a server, aclient, an industrial module, a human machine interface (HMI), agraphical user interface (GUI), and so forth.

The host 102 can be configured to execute at least one service 106based, at least in part, on input from the user 104. The service 106 isillustrated as contained within a platform 108, which can provide aninterface between the host 102 and the service 106. For example, theservice 106 can be an executable function for the industrial automationsystem 100 executed on a platform 108 of the host 102. By providing theinterface between the host 102 and the service 106, the platform 108provides a set of abstractions that enable the service 106 to beimplemented (e.g., compiled and executed) in disparate hosts withoutmodification to the service. The platform 108 can be any type ofhardware, software, or combination of hardware and software that allowsthe service 106 to run and/or execute, for example, in some embodiments,the platform 108 can be the Java™ programming language and computingplatform. For example, the platform 108 can include one or more of acomputer's architecture, an operating system, one or more programminglanguages, or user interfaces.

The service 106 can be employed as one or more executable functions forthe industrial automation system 100. In accordance with some aspects,the service 106 is a reusable template that can be utilized in thedevelopment of software for the industrial automation system 100. Thesoftware can include, for example, control programs for physicalmanufacturing unit operations, such as assembly applications. Thephysical manufacturing unit can include, for example, conveyors, mixers,packaging units, process skids, robotic cells, tanks, valve matrices,and so forth. Additionally or alternatively, the software can includehigher-level programs, such as batch processing applications,supervisory applications, monitoring applications, or control programsthat control aspects of the industrial automation system 100.

According to some aspects, the service 106 can include one or moremodule objects, encapsulated objects, control objects, and so on. Theservice 106 can be configured to facilitate software development byhiding internal interfaces, messages, programming code, and so forthfrom the user 104 while providing standard and/or generic externalinterface(s). In accordance with some aspects, the service 106 cansimplify programming in the industrial automation system 100 by allowingthe user 104 (e.g., a process and control engineer) to work withpublished functionality of the service 106, which can be independent ofhow the functionality was achieved, which can mitigate integration andmaintenance requirements and reduce costs. This can increase quality,consistency, and reusability of the software by providing a standardizedprogramming structure between various components or hosts 102 (e.g.,from different manufacturers) within the industrial automation system100.

For example, utilizing services 106 can benefit both software developersand end users. For example, utilization of services can allow adeveloper of control applications to concentrate on the functionality ofan application rather than the mechanics of implementation, such as byseparating procedure control and equipment control. Services 106 canfacilitate continuous software improvements; at the same time, services106 can mitigate the risks that changes to the software may present tothe industrial automation system 100. Utilization of services, asdisclosed herein can simplify testing of software, and can provide areduced chance that new software adversely affects other components orhosts 102 within the industrial automation system 100. This can alsoreduce development time, accelerate design cycles, and reduce cost.Services 106 can also allow end users (e.g., manufacturers) to separateprocedural control from equipment control, which can allow end users toadopt existing assets to new product requirements with minimal time andcapital investment.

According to various aspects, the service 106 can separate proceduralcontrol from equipment control by employing a hierarchically structureddata model (e.g., a hierarchically structured data model according tothe International Society for Automation (ISA)-88 standards). In such amanner, procedural control can be logically separated from equipmentcontrol. Logical separation can enable the separation ofproduct-specific definitions, instructions, and information fromprocessing equipment entities.

The service 106 can be configured to hide internal aspects from a user104. For example, the service 106 (and/or platform 108) can include orcan be associated with one or more interfaces. In accordance with someaspects, the one or more interfaces can be located within the host 102.The one or more interfaces can hide internal functions of the service106, including the underlying code and complexity. According to anembodiment, the one or more interfaces can define external behaviorssupplied to at least one client application engaging the service 106.Through the one or more interfaces, the service 106 can expose data,expose operations that can be performed, expose dependencies on otherservices, and so forth. The one or more interfaces can allow the service106 to connect to at least one other service to engage with a clientapplication, according to an aspect. For example, an industrial processcan be defined with a plurality of services, wherein a first service isa control service that controls a second service (e.g., equipmentservice) and a third service (e.g., material service), wherein the thirdservice is subordinate to the second service. It is to be appreciatedthat the service 106 can support more than one interface, for example,to engage with more than one client application or to logicallypartition the functionality of the service. In some aspects, a singleinterface can support a plurality of clients. Separation of a serviceinto multiple interfaces can allow one interface to be extended and/orchanged without impacting other interface areas. Such separation canmitigate the overall impact to areas of an industrial automation systemthat utilize the unchanged interface, but not the changed interface.

The interface can hide internal functions of the service 106. Theseinternal functions can include one or more reusable definitions 110 andone or more specifications 112. In accordance with some aspects, theservice 106 can be an association of one or more reusable definitions110 with one or more specifications 112. The one or more reusabledefinitions 110 can include program code that can alter the state of oneor more resources in an industrial automation system (e.g., logic codethat can control opening and closing of a valve). The one or morereusable definitions 110 can include programming code, for example,ladder logic, function chart, script, Java™ C code, and so on. The oneor more specifications 112 can include the one or more resources. Theone or more resources can include one or more of equipment, material,personnel, segments, storage, and so forth. For example, the resourcemay be a valve that is opened or closed according to logic code.

In accordance with some aspects, the programming code of the reusabledefinition 110 can be in a different physical location from the resourceof the specification 112 within an enterprise resource control (ERC)system. It is to be appreciated that the service 106 can support morethan one reusable definition 110. According to some aspects, differentreusable definitions 110 can be targeted for different hosts such that aservice 106 with more than one reusable definition 110 can be deployedto more than one host 102 where each host may have different computingcapabilities and methods.

The service 106 can include external references (not illustrated) thatcan maintain metadata pertaining to the service 106, according to anaspect. For example, the external references can include informationthat describes dependencies of the service 106, required dependencies tosupport the reusable definitions 110 (e.g., operational requirements).The external references can also include, for example, specificqualities (e.g., performance, reliability, physical characteristics, andso forth) of the service 106 and/or security aspects (e.g., securityrules and automatic application thereof, or authentication procedures)of the service 106. The service 106 may also include other portions (notshown), such as local data, visualization elements, etc. Alternatively,a service 106 may be more limited in nature (e.g., only including asingle specification 112).

FIG. 2 illustrates an example system 200, according to an aspect. System200 can be a portion of an industrial control configuration of anindustrial automation system. Included in system 200 are services 202(e.g., modular objects, encapsulated objects, control objects, etc.)that can exist in conjunction with a one or more hosts 204 upon anindustrial control configuration. For example, the services 202 canexist in conjunction with the hosts 204 through an interface 206.Functionality related to the services 202 can be similar to plug-inapproaches in software. For example, services 202 can be connected tocontrol a process in the industrial control environment. Services 202can be customizable and reusable, for example, among multiple users,multiple locations, multiple platforms, and/or multiple hosts 204.

The services 202 can grow into different layers of an organizationalhierarchy to form a service oriented control system. For example, anindustrial process can be defined with a plurality of services 202,wherein one service is a control service, which controls an equipmentservice and a material service, wherein the material service issubordinate to the equipment service.

Generally, the service 202 is an association of one or more reusabledefinitions 208 with one or more specifications 210. Reusabledefinitions 208 can include program code that can alter a state of oneor more resources in the industrial control environment. For example,the reusable definitions 208 can be at least one of logic code,including ladder logic, function chart, script, Java™, C code, and thelike. It is to be appreciated that a service 202 can support multiplereusable definitions 208 (e.g., to engage with multiple hosts 204). Theone or more specifications 210 can include the one or more resources.The one or more resources can include one or more of equipment,material, personnel, segments, storage, and the like. For example, theresource may be a valve that is opened or closed according to logiccode.

Similar to a plug-in approach in software, a service 202 can hideinternal aspects (e.g., reusable definitions 208 and specifications 210)from a user. The service 202 can hide these aspects by providingstandard and/or generic interfaces 206 to external systems. According toan embodiment, the interface 206 can allow the service 202 to exposeexternal reference information about the service 202. For example, theexternal reference information can include information describingdependencies of the service 202, required connections to support thereusable definition 208, and the like. The service 202 can supportmultiple interfaces 206, which can allow the service 202 to engage withmultiple hosts 204.

According to an embodiment, users and/or hosts 204 can access theservices 202 across a network (not shown). The network may include, forexample, any public or private network. For example, services 202 can becreated in an offline manner, such as in a computer database (notshown). When created offline, the services 202 can be downloaded forexecution on the hosts 204.

FIG. 3 illustrates an example system 300 for expressing matching amonghosts 302 and a service 304. The service 304 can have one or moreoperational requirements 306. For example, the operational requirements306 can be that a host should have a high resolution size and a largememory. Hosts 302 can have different capabilities 308 that can beexploited by the service 304. A binding (represented with a dotted line)can be created with a host in an attempt to match one or moreoperational requirement 306 with one or more capabilities 308. If morethan one host 302 includes one or more capabilities 308 that match oneor more operational requirements 306 of a service 304, then multiplebindings can be created and/or selection of a single host can occur andone binding can be used. If no host 302 has a capability 308 matching anoperational requirement 306 of the service 304, then an error messagecan be generated. In accordance with some aspects, if there are nocurrent hosts 302 that match an operational requirement 306, periodic orcontinuous observation of the environment can occur to detect when a newhost 302 that has the required capability 308 enters the environment.The periodic or continuous monitoring can also occur to detectmodifications to an existing host 302 to determine when the host 302 hasbeen modified and now meets at least one operational requirement 306 ofthe service 304.

FIG. 4 illustrates an example industrial control system 400 thatsupports multiple platform configurations, according to an aspect.Support of multiple interfaces associated with multiple services andrelated platform configurations enables grouping and namespaceseparation. Multiple platform configurations can also support visibilitycontrols, which can allow different users access to different sets ofcontrols and objects. Platform configurations can be tagged to providedifferent functionality depending on the intended use of the platformconfigurations. Multiple platform configurations also enable scalableupdating. Traditionally, the entire industrial control system is updatedin response to changes in implementation of one or more of software,hardware, or firmware, necessary to operate the industrial system.However, with the one or more disclosed aspects, service(s) andassociated platform configuration(s) are decoupled, which allowsindividual platform configurations to be revisioned (e.g., updated)separately. The decoupled platform configuration(s) allow each platformconfiguration to be reused with different implementations (e.g.,implementation of software or firmware) and objects. Additionally oralternatively, the platform configuration(s) can reuse specific methodsin which reusable definitions contain only the definitions of operation.This is a more granular approach than the approach traditionallyperformed (e.g., where whole services are reused).

Included in industrial control system 400 is a device 402 that interactswith multiple platform configurations 404. Each of the differentplatform configurations 404 can be utilized with different host(s) 406within the industrial control system 400 (or within a relatedarchitecture). In accordance with some aspects, a single host 406 isutilized with multiple platform configurations 404. Although variousaspects herein illustrate connections between device 402, platformconfigurations 404, and host(s) 406 as wireless links, according to someaspects, the links can be wireline links, or both wireless and wirelinelinks, or might be on the same physical machine and use memory or othertechniques suitable for communication.

The multiple platform configurations 404 can include one or moreservices 408 associated with one or more reusable definitions 410 and/orone or more specifications 412. In accordance with some aspects,different platform configurations 404 can use a common service 408, acommon reusable definition 410, a common specification 412, orcombinations thereof. Each component (e.g., service, reusabledefinition, specification) of the platform can be located anywherewithin an industrial control system 400 and does not need to beco-located with other components of the platform and/or the host(s) 406.

Device 402 comprises an interface component 414 that is configured toprovide a set of functional connections and controls for variousautomated host implementations, wherein the automated hostimplementations are configured to interact with a plurality of platformconfigurations. In accordance with some aspects, the automatedimplementation of the host is execution of a service that comprises areusable definition and a specification. Interface component 414 canprovide a mechanism for interaction between a user and/or entity (e.g.,the Internet, another system, a computer, and so on, hereinafterreferred to as user), the one or more hosts 406, and the multipleplatform configurations 404. For instance, the interface component 414can be, but is not limited to being, a keyboard, a mouse, apressure-sensitive screen, a graphical user interface, a microphone, andvoice recognition software. In accordance with some aspects, the one ormore hosts 406 and the device 402 can be in separate locations withinthe industrial control system 400 or another location (e.g., satelliteplant, vendor location, client location, and so forth).

In accordance with some aspects, device 402 is configured to be utilizedfor one host 406, wherein the device 402 is independent of theimplementation and is transparent to the end user. In such a manner,device 402 can be reused on multiple hosts that are functionalequivalents but that may have fundamental underlying differences. Thus,logic can be implemented in different languages, different softwarebases, and so forth.

Also included in device 402 is a deployment component 416 that isconfigured to support a plurality of platform configurations 404.Further, the deployment component 416 can be functionally independent ofthe platform configurations 404. For example, deployment component 416can be configured to be reused on multiple platform configurations thatare functional equivalents, but have underlying differences. Forexample, at least one multiple platform configuration can have adifferent programming language than at least one other of the multipleplatform configurations. However, even though the platformconfigurations have different programming languages, the deploymentcomponent 416 is configured to support both languages and, therefore,both platform configurations. In accordance with some aspects,deployment component 416 does not support each individual language butinstead utilizes a high-level programming code that can interface withmultiple programming languages without being programming languagespecific.

Additionally or alternatively, deployment component 416 can beconfigured to support platform configurations having differentimplementations. For example, one implementation can be in an industrialautomated controller and a second implementation can be in a softwaresystem. The support of different implementations can allow an endapplication to be indifferent or unbound to a current implementation onanother end application.

According to some aspects, deployment component 416 can be configured tocapture a command or action regardless of how the command or action isused. For example, an action might be that if a certain conditionoccurs, an alarm (e.g., a specification) is activated. A similarspecification (e.g., alarm) can be employed when a different eventoccurs. Even though a similar specification (e.g., alarm) is used inboth cases, the deployment component 416 allows the reusable definitionto interact with the specification (e.g., alarm) even though thespecification is being utilized differently by two different automatedhost implementations.

In accordance with some aspects, deployment component 416 can aggregateone or more services 408, one or more reusable definitions 410, and/orone or more specifications 412. The aggregation can include identifyingtwo or more services, two or more reusable definitions, and/or two ormore specifications that are similar and determining that the similarservices, reusable definitions, and/or specifications can be aggregatedor utilized interchangeably. In accordance with some aspects, deploymentcomponent 416 aggregates based at least in part on a languagerequirement of an implementation of the at least one service. Accordingto some aspects, deployment component 416 aggregates based at least inpart on metadata related to an implementation of the at least oneservice. In some aspects, deployment component 416 aggregates based atleast in part on an analysis of the at least one of a plurality ofcapabilities. In additional or alternative aspects, deployment component416 aggregates in response to definition of user-specific configurationof industrial control system 400.

Aggregation of a group of services results in a composite service, orcomposite object. The composite service includes at least one interfacefrom each of the services in the group of services. As indicated supra,deployment component 416 can aggregate the group of services. Inaddition, in certain embodiments, deployment component 416 can managethe at least one interface of each of the services in the group ofservices. The management can be effected in accordance with twoapproaches: (1) Compact. The set of interfaces spanned by the at leastone interface of each of the services in the group of services can formthe composite service with a single, compact interface associated withthe composite service. In this approach, at least a sub-set of one ormore interface(s) in the set of interfaces are hidden and not availableto users (machine or human agent) disjointedly from, or outside, thecomposite service. (2) Loose. Each interface in the set of interfacesspanned by the at least one interface of each of the services in thegroup of services is transferred intact into the composite service. Suchset of interfaces embody the interface of the composite service; thecomposite service retains the interface(s) in the set of interfaces asindividual entities. Each interface can be exposed as part of formationof the composite service, but remains hidden otherwise.

In order to visualize a group of alternative platform configurationpossibilities and/or aggregation of at least a portion of platformconfigurations, FIG. 5 illustrates a schematic representation 500 of anexample group of alternative platform configurations, according to anaspect. Illustrated in the schematic representation 500 are multiplehosts, labeled Host₁ 502 and Host_(N) 504, where N is an integer equalto or greater than one. Host₁ 502 can utilize a first service 506, whichutilizes a first reusable definition 508, which utilizes a specification510 (e.g., creating a platform configuration that comprises service 506,reusable definition 508, and specification 510). In a similar manner,Host_(N) 504 can utilize a second service 512, which utilizes a secondreusable definition 514, which utilizes the specification 510. However,in accordance with some aspects, another possibility for a platformconfiguration is that Host_(N) 504 can utilize first service 506 asindicated at 516. In a similar manner, Host₁ 502 can alternativelyutilize second service 512. Further second service 512 mightalternatively utilize first reusable definition 508, as indicated at518. In a similar manner, first service 506 might alternatively utilizesecond reusable definition 514. In accordance with some aspects, a hostmight utilize more than on service, more than one reusable definition,one or more specifications, or combinations thereof.

FIG. 6 illustrates an industrial automation system 600 that isconfigured to support multiple interfaces and/or multiple interfaceversions at run-time, according to an aspect. Support of multipleinterfaces and/or multiple interface versions during runtime can enablethe support without the need to shut down a machine or a device, whichcan save time as well as associated costs (e.g., loss of production,loss of manpower, and so forth). For example, live updates can beapplied to one of the interfaces (e.g., an updated version or newrevision of the interface) and can be tested during runtime. If the testdoes not operate as expected or if other problems occur, system 600 canautomatically revert to an older format interface for which support hasbeen retained.

Included in system 600 is a device 602 that is configured to operate inan industrial automation system or another system. Device 602 can beassociated with one or more hosts 604 and at least one service 606. Theat least one service 606 can comprise at least one reusable definition608 and at least one specification 610. In accordance with some aspects,service 606 can be internal to device 602, however, service 606 can beexternal to device 602, as illustrated. Although the connections betweenthe device 602, the host(s) 604, and the service(s) 606 are illustratedas wireless links, according to some aspects, the links can be wirelinelinks, or both wireless and wireline links, or might be on the samephysical machine and use memory or other techniques suitable forcommunication.

Device 602 comprises an interface component 612 that is configured toobtain a set of alternative interface applications for industrialautomation system 600. The set of alternative interface applications isillustrated as a first interface application 614, a second interfaceapplication 616, and a third (or subsequent) interface application 618,however, the disclosed aspects are not limited to three interfaceapplications and fewer or more interface applications can be supportedby device 602 in accordance with the disclosed aspects. Each interfaceapplication 614, 616, 618 in the set of alternative interfaceapplication can be a different interface version associated with the atleast one service(s) 606, the reusable definition(s) 608, and/or thespecification(s) 610.

Examples of different interface versions that can be applied, accordingto an aspect, is shown in FIG. 7, which illustrates an example schematicrepresentation 700 of a system that is configured to provide multipleinterface support, according to an aspect. System 700 includes at leastone service 702 that comprises one or more reusable definitions 704 andone or more specifications 706. Service 702 is configured to implementand support multiple interface applications. For example, a firstversion of an interface application 708 (interface V1.0) is obtained anddeployed with service 702.

The first version of the interface application 708 can be edited(on-line or off-line) to produce a second version of the interfaceapplication 710 (interface V1.1). A mapping 712 can be provided betweenthe second version of the interface application 710 and the firstversion of the interface application 708. The mapping 712 provides amechanism to translate (e.g., transform, cross-reference) informationbetween revisions of the interface (e.g., between first version ofinterface application 708 and second version of interface application710). Subsequent revisions of interface applications 714 (e.g.,interface V1.2) can be produced or obtained (e.g., downloaded) andassociated with service 702. A mapping 716 (similar to the mappingbetween first interface application 708 and second interface application710) is retained between second interface application 710 and thirdinterface application 714.

The mappings 712, 716 allow the service 702 (or a device) to continue tosupport clients associated with each of the different revisions,illustrated as first client(s) interface 718 (V1.0), second client(s)interface 720 (V1.1), third client(s) interface 722 (V1.2). Theclient(s) interfaces interact with one or more of the revisions of theinterface applications.

At major interface revisions, shown as (fourth) interface application724 (e.g., interface V2.0 and associated client(s) interface V2.0 726),such transformations/adaptations may not be possible. The majorinterface revision can necessitate “breaking change” where mappinglayers 712, 716 are not provided between a previous interface versionand the major interface revision. Thus, there is no cross-referencebetween the major interface revision and the previous revisions,according to an aspect. In this scenario, the existing interfaceversions (e.g., first interface application, second interfaceapplication, third interface application, and so on) continues toservice the clients, regardless of the interface revisions those clientsrequire (e.g., there is still support for the application interfaces forwhich client support is needed).

Referring again to FIG. 6, to obtain the set of alternative interfaceapplications, interface component 612 can include a validation component620 that is configured to perform a compatibility check of eachinterface application when the interface application becomes available.For example, a notification can be received by interface component 612(or another component of device 602) that provides notice of a newinterface application or a revision to a previous interface application.The notice can be received from service(s) 610, from host(s) 604, orfrom another entity within system 600.

Validation component 620 can compare the new interface application(e.g., second interface application 616) to an existing application(e.g., first interface application 614) to determine compatibilitybetween the interface applications. If validation component 620determines there is compatibility, approval of the interface application(e.g., second interface application 616) is provided to a downloadcomponent 622 that obtains the interface application.

In accordance with some aspects, validation component 620 can receive arequest to test an interface selected from a set of alternativeinterfaces. The request can be received from a user and/or can beautomatically inferred based on a defined outcome (e.g., a desired endresult). In accordance with some aspects, the request is received froman Original Equipment Manufacturer (OEM) that is authorized to interactwith system 600. For example, the OEM might be performing an update toits machinery and would like to perform testing within system 600.

Download component 622 is configured to obtain information related tofirst interface application 614, second interface application 616, thirdinterface application 618, and/or other interface applications. Downloadcomponent 622 can also receive information related to the one or morehosts 604. In accordance with some aspects, download component 622receives the interface applications in the form of updates. The updatescan be received though a web-based subscription, according to an aspect,wherein download component 622 selectively downloads the updates (e.g.,interface applications). For example, if the update is approved byvalidation component 620 the update is download. In another example, ifvalidation component 620 does not approve the update, the update is notdownload and an error message or other indication that the update willnot be applied by device 602 can be conveyed to the user though host 604or through another means perceivable by the user.

Also included in device can be a mapping component 624 that isconfigured to translate information between each interface application.For example, the mapping component 624 can maintain information relatedto a revision level of each interface application. In accordance withsome aspects, mapping component 624 is associated with a memory 626 thatmaintain information related to the interface applications, wherein theinformation include the mapping or cross-reference between the interfaceapplications.

Device 602 also comprises a deployment component 628 that is configuredto utilize an interface application (e.g., second interface application616, third interface application 618) while support for an existinginterface application (e.g., first interface application 614, secondinterface application 616) is maintained. This can allow support for twoor more interface applications without having to deploy an entirely newinterface application (or service) that might not be suitable orcompatible with the other interface application or services. Deploymentcomponent 628 can provide runtime testing of the second interfaceapplication 616 (or subsequent interface application), which can allowfor validation of the second (or subsequent) interface application 616before that interface application is utilized with the device 602. Sincethe architecture is modular, the interface applications can be comparedand contrasted before the updated interface application (e.g., secondinterface application 616, third interface application 618) isdownloaded and/or implemented within system 600. If the interfaceapplication being tested is not suitable, a toggle module 630 isconfigured to dynamically switch from the interface application beingtested (e.g., second interface application 616, third interfaceapplication 618) to the previous version interface application (e.g.,first interface application 614, second interface application 616).

In accordance with some aspects, second interface application 616 iscompared with a plurality of alternative interface applications in orderto determine whether second interface application 616 is suitable orwhether one of the alternative interfaces should be utilized instead(e.g., first interface application 614, third interface application 618,or another interface application). In this aspect, deployment component628 is configured to select one of the multiple versions of interfaceapplications to utilize depending on a desired result, wherein aparticular interface application has been identified as suitable for thedesired result.

In accordance with some aspects, interface component 612 providesmultiple views through the device 602 or host(s) 604. The views can beeither logic views or host views using the same tool, depending on anaccess level of the user (e.g., based on a validation, access codeinformation, and so forth). The modules can be HMI screens that executeon display hardware or can be executed in a logic controller, or on anapplication server.

In another aspect, interface component 612 provides metadata withinformation relating to accessibility that can be associated with theinterface. The metadata can include information related to whether theinterface is read only, write only, read-write, and so forth. Themetadata can be discoverable by other components, according to anaspect.

In view of exemplary systems shown and described above, methods that maybe implemented in accordance with the disclosed subject matter, will bebetter appreciated with reference to various flow charts. While, forpurposes of simplicity of explanation, methods are shown and describedas a series of blocks, it is to be understood and appreciated that thedisclosed aspects are not limited by the number or order of blocks, assome blocks may occur in different orders and/or at substantially thesame time with other blocks from what is depicted and described herein.Moreover, not all illustrated blocks may be required to implementmethods described herein. It is to be appreciated that functionalityassociated with blocks may be implemented by software, hardware, acombination thereof or any other suitable means (e.g. device, system,process, component). Additionally, it should be further appreciated thatmethods disclosed throughout this specification are capable of beingstored on an article of manufacture to facilitate transporting andtransferring such methods to various devices. Those skilled in the artwill understand and appreciate that a method could alternatively berepresented as a series of interrelated states or events, such as in astate diagram.

FIG. 8 illustrates a method 800 for dynamically switching betweenmultiple interface applications, according to an aspect. Dynamicswitching can be utilized to maintain multiple versions of an interface.This can allow runtime testing of different interface applications aswell as other benefits (e.g., automatic switching between interfaceapplications to provide different results such as a change in materialbeing run in an industrial control environment in order to meet clientchange requests or different client products). In accordance with someaspects, dynamic switching can facilitate forwarding and/or routingacross interface application versions or revision levels. Dynamicswitching can also provide backward and forward compatibility checksand/or validations between interface applications. Further, dynamicswitching can provide on-line editing of an interface application.

Method 800 starts, at 802, when a first interface application for anindustrial automation system is received. The first interfaceapplication is deployed, at 804. A second interface application isobtained, at 806. The second interface application can be obtained bydownloading an update that comprises the second interface application.In accordance with some aspects, the second interface application can bereceived based on a user request for a desired outcome, wherein a changeto the first interface application was performed (resulting in thesecond (or subsequent) interface application) in order to comply withthe user request. In accordance with some aspects, the second (orsubsequent) interface application is obtained based on an update that isto occur within the industrial control system (e.g., a new revisionlevel). According to some aspects, the second (and subsequent) interfaceapplication is obtained in the form of an update that is downloaded. Theupdate(s) can be delivered via a web-based subscription, according to anaspect.

At 808, a mapping between the first interface application and the second(or subsequent) interface application is developed and retained. Theinformation can include information related to a revision level of theinterface application, specific information related to a differencebetween the first and second (or subsequent) interface applications,and/or other information that can help validate interface applications.In accordance with some aspects, the information and/or mapping isretained in a computer-readable storage medium. Retaining theinformation can include storing information related to a first revisionlevel of the first interface application and a second revision level ofthe second interface application.

The second interface application is enabled, at 810. The enabling caninclude testing the second interface application during runtime. Inaccordance with some aspects, the second (or subsequent) interfaceapplication is enabled while support for a previous (e.g., first)interface application is retained. In accordance with some aspects, theenabling comprises retaining support for the first interfaceapplication. According to some aspects, the enabling comprisesperforming a test of the second interface application during runtime.

If the enabled (e.g., second) interface application does not perform asexpected or is to be disabled for another reason (e.g., testing isconcluded), at 812, operation with an existing (e.g., first) interfaceapplication is resumed. The existing interface application can be one ormore interface applications from a set of alternative interfaceapplications that were in operation before the test began. Theresumption of the existing interface application allows for dynamicswitching between new interface application and old interfaceapplications (e.g., to facilitate updating from an old interfaceapplication to a new interface application).

In accordance with some aspects, the dynamic switching can be performedduring runtime, which can allow the use of multiple interfaceapplication without shutting down a device or machine, for example. Liveupdates can be applied to one of the interface applications, which canbe tested during runtime. If the test does not operate as expected, theinterface application can be automatically reverted to the old format orrevision level. In accordance with some aspects, a interface applicationcan be extended while support for the existing interface application ismaintained, which can mitigate the need to deploy an entirely newservice. Since the architecture is modular, the interface applicationcan be compared and contrasted before the updated interface applicationneeds to be downloaded.

Other features include multiple views through the device. The views canbe either logic views or machine views using the same tool, depending onan access level of the user (e.g., based on a validation, access codeinformation, and so forth). The modules can be HMI screens that executeon display hardware or can be executed in a logic controller, or on anapplication server.

Another aspect provides metadata with information relating toaccessibility that can be associated with the interface application. Themetadata can include information related to whether the interfaceapplication is read only, write only, read-write, and so forth. Themetadata can be discoverable by other components, according to anaspect.

Referring now to FIG. 9, illustrated is a block diagram of a computeroperable to execute the disclosed system. In order to provide additionalcontext for various aspects thereof, FIG. 9 and the following discussionare intended to provide a brief, general description of a suitablecomputing environment 900 in which the various aspects of theembodiment(s) can be implemented. While the description above is in thegeneral context of computer-executable instructions that may run on oneor more computers, those skilled in the art will recognize that thevarious embodiments can be implemented in combination with other programmodules and/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the inventive methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the various embodiments may also be practicedin distributed computing environments where certain tasks are performedby remote processing devices that are linked through a communicationsnetwork. In a distributed computing environment, program modules can belocated in both local and remote memory storage devices.

Computing devices typically include a variety of media, which caninclude computer-readable storage media and/or communications media,which two terms are used herein differently from one another as follows.Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disk (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or other tangible and/or non-transitorymedia which can be used to store desired information. Computer-readablestorage media can be accessed by one or more local or remote computingdevices, e.g., via access requests, queries or other data retrievalprotocols, for a variety of operations with respect to the informationstored by the medium.

Communications media typically embody computer-readable instructions,data structures, program modules, or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of its characteristics set or changedin such a manner as to encode information in one or more signals. By wayof example, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

With reference again to FIG. 9, the illustrative environment 900 forimplementing various aspects includes a computer 902, the computer 902including a processing unit 904, a system memory 906 and a system bus908. The system bus 908 couples system components including, but notlimited to, the system memory 906 to the processing unit 904. Theprocessing unit 904 can be any of various commercially availableprocessors. Dual microprocessors and other multi-processor architecturesmay also be employed as the processing unit 904.

The system bus 908 can be any of several types of bus structure that mayfurther interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 906 includesread-only memory (ROM) 910 and random access memory (RAM) 912. A basicinput/output system (BIOS) is stored in a non-volatile memory 910 suchas ROM, EPROM, EEPROM, which BIOS contains the basic routines that helpto transfer information between elements within the computer 902, suchas during start-up. The RAM 912 can also include a high-speed RAM suchas static RAM for caching data.

The computer 902 further includes an internal hard disk drive (HDD) 914(e.g., EIDE, SATA), which internal hard disk drive 914 may also beconfigured for external use in a suitable chassis (not shown), amagnetic floppy disk drive (FDD) 916, (e.g., to read from or write to aremovable diskette 918) and an optical disk drive 920, (e.g., reading aCD-ROM disk 922 or, to read from or write to other high capacity opticalmedia such as the DVD). The hard disk drive 914, magnetic disk drive 916and optical disk drive 920 can be connected to the system bus 908 by ahard disk drive interface 924, a magnetic disk drive interface 926 andan optical drive interface 928, respectively. The interface 924 forexternal drive implementations includes at least one or both ofUniversal Serial Bus (USB) and IEEE 1094 interface technologies. Otherexternal drive connection technologies are within contemplation of thevarious embodiments described herein.

The drives and their associated computer-readable media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 902, the drives and mediaaccommodate the storage of any data in a suitable digital format.Although the description of computer-readable media above refers to aHDD, a removable magnetic diskette, and a removable optical media suchas a CD or DVD, it should be appreciated by those skilled in the artthat other types of media which are readable by a computer, such as zipdrives, magnetic cassettes, flash memory cards, cartridges, and thelike, may also be used in the illustrative operating environment, andfurther, that any such media may contain computer-executableinstructions for performing the methods of the disclosed subject matter.

A number of program modules can be stored in the drives and RAM 912,including an operating system 930, one or more application programs 932,other program modules 934 and program data 936. All or portions of theoperating system, applications, modules, and/or data can also be cachedin the RAM 912. It is to be appreciated that the various embodiments canbe implemented with various commercially available operating systems orcombinations of operating systems.

A user can enter commands and information into the computer 902 throughone or more wired/wireless input devices, e.g., a keyboard 938 and apointing device, such as a mouse 940. Other input devices (not shown)may include a microphone, an IR remote control, a joystick, a game pad,a stylus pen, touch screen, or the like. These and other input devicesare often connected to the processing unit 904 through an input deviceinterface 942 that is coupled to the system bus 908, but can beconnected by other interfaces, such as a parallel port, an IEEE 1094serial port, a game port, a USB port, an IR interface, etc.

A monitor 944 or other type of display device is also connected to thesystem bus 908 via an interface, such as a video adapter 946. Inaddition to the monitor 944, a computer typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 902 may operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 948. The remotecomputer(s) 948 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer902, although, for purposes of brevity, only a memory/storage device 950is illustrated. The logical connections depicted include wired/wirelessconnectivity to a local area network (LAN) 952 and/or larger networks,e.g., a wide area network (WAN) 954. Such LAN and WAN networkingenvironments are commonplace in offices and companies, and facilitateenterprise-wide computer networks, such as intranets, all of which mayconnect to a global communications network, e.g., the Internet.

When used in a LAN networking environment, the computer 902 is connectedto the local network 952 through a wired and/or wireless communicationnetwork interface or adapter 956. The adaptor 956 may facilitate wiredor wireless communication to the LAN 952, which may also include awireless access point disposed thereon for communicating with thewireless adaptor 956.

When used in a WAN networking environment, the computer 902 can includea modem 958, or is connected to a communications server on the WAN 954,or has other means for establishing communications over the WAN 954,such as by way of the Internet. The modem 958, which can be internal orexternal and a wired or wireless device, is connected to the system bus908 via the serial port interface 942. In a networked environment,program modules depicted relative to the computer 902, or portionsthereof, can be stored in the remote memory/storage device 950. It willbe appreciated that the network connections shown are illustrative andother means of establishing a communications link between the computerscan be used.

The computer 902 is operable to communicate with any wireless devices orentities operatively disposed in wireless communication, e.g., aprinter, scanner, desktop and/or portable computer, portable dataassistant, communications satellite, any piece of equipment or locationassociated with a wirelessly detectable tag (e.g., a kiosk, news stand,restroom), and telephone. This includes at least Wi-Fi and Bluetooth™wireless technologies. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

Wi-Fi, or Wireless Fidelity, allows connection to the Internet withoutwires. Wi-Fi is a wireless technology similar to that used in a cellphone that enables such devices, e.g., computers, to send and receivedata indoors and out; anywhere within the range of a base station. Wi-Finetworks use radio technologies called IEEE 802.11x (a, b, g, etc.) toprovide secure, reliable, fast wireless connectivity. A Wi-Fi networkcan be used to connect computers to each other, to the Internet, and towired networks (which use IEEE 802.3 or Ethernet).

Wi-Fi networks can operate in the unlicensed 2.4 and 5 GHz radio bands.IEEE 802.11 applies to generally to wireless LANs and provides 1 or 2Mbps transmission in the 2.4 GHz band using either frequency hoppingspread spectrum (FHSS) or direct sequence spread spectrum (DSSS). IEEE802.11a is an extension to IEEE 802.11 that applies to wireless LANs andprovides up to 54 Mbps in the 5 GHz band. IEEE 802.11a uses anorthogonal frequency division multiplexing (OFDM) encoding scheme ratherthan FHSS or DSSS. IEEE 802.11b (also referred to as 802.11 High RateDSSS or Wi-Fi) is an extension to 802.11 that applies to wireless LANsand provides 11 Mbps transmission (with a fallback to 5.5, 2 and 1 Mbps)in the 2.4 GHz band. IEEE 802.11g applies to wireless LANs and provides20+ Mbps in the 2.4 GHz band. Products can contain more than one band(e.g., dual band), so the networks can provide real-world performancesimilar to the basic 10BaseT wired Ethernet networks used in manyoffices.

Referring now to FIG. 10, there is illustrated a schematic block diagramof an illustrative computing environment 1000 for processing thedisclosed architecture in accordance with another aspect. Theenvironment 1000 includes one or more client(s) 1002. The client(s) 1002can be hardware and/or software (e.g., threads, processes, computingdevices). The client(s) 1002 can house cookie(s) and/or associatedcontextual information in connection with the various embodiments, forexample.

The environment 1000 also includes one or more server(s) 1004. Theserver(s) 1004 can also be hardware and/or software (e.g., threads,processes, computing devices). The servers 1004 can house threads toperform transformations in connection with the various embodiments, forexample. One possible communication between a client 1002 and a server1004 can be in the form of a data packet adapted to be transmittedbetween two or more computer processes. The data packet may include acookie and/or associated contextual information, for example. Theenvironment 1000 includes a communication framework 1006 (e.g., a globalcommunication network such as the Internet) that can be employed tofacilitate communications between the client(s) 1002 and the server(s)1004.

Communications can be facilitated via a wired (including optical fiber)and/or wireless technology. The client(s) 1002 are operatively connectedto one or more client data store(s) 1008 that can be employed to storeinformation local to the client(s) 1002 (e.g., cookie(s) and/orassociated contextual information). Similarly, the server(s) 1004 areoperatively connected to one or more server data store(s) 1010 that canbe employed to store information local to the servers 1004.

It is noted that as used in this application, terms such as “component,”“module,” “system,” and the like are intended to refer to acomputer-related, electro-mechanical entity or both, either hardware, acombination of hardware and software, software, or software in executionas applied to an automation system for industrial control. For example,a component may be, but is not limited to being, a process running on aprocessor, a processor, an object, an executable, a thread of execution,a program and a computer. By way of illustration, both an applicationrunning on a server and the server can be components. One or morecomponents may reside within a process or thread of execution and acomponent may be localized on one computer or distributed between two ormore computers, industrial controllers, or modules communicatingtherewith.

Furthermore, the term “set” as employed herein excludes the empty set;e.g., the set with no elements therein. Thus, a “set” in the subjectdisclosure includes one or more elements or entities. As anillustration, a set of controllers includes one or more controllers; aset of data resources includes one or more data resources; etc.Likewise, the term “group” as utilized herein refers to a collection ofone or more entities; e.g., a group of nodes refers to one or morenodes.

The subject matter as described above includes various exemplaryaspects. However, it should be appreciated that it is not possible todescribe every conceivable component or methodology for purposes ofdescribing these aspects. One of ordinary skill in the art may recognizethat further combinations or permutations may be possible. Variousmethodologies or architectures may be employed to implement the subjectinvention, modifications, variations, or equivalents thereof.Accordingly, all such implementations of the aspects described hereinare intended to embrace the scope and spirit of subject claims.Furthermore, to the extent that the term “includes” is used in eitherthe detailed description or the claims, such term is intended to beinclusive in a manner similar to the term “comprising” as “comprising”is interpreted when employed as a transitional word in a claim.

What is claimed is:
 1. A system, comprising: a processor; and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising:implementing a first interface application within an industrialautomation environment; changing implementation from the first interfaceapplication to a second interface application based on a determinationthat the second interface application is compatible with the firstinterface application; and reverting operation of the industrialautomation environment to the first interface application based ondetection of an occurrence of a defined event.
 2. The system of claim 1,further comprises storing information related to a first service of thefirst interface application and a second service of the second interfaceapplication, wherein the first service and the second service compriserespective reusable definitions and respective specifications thatcomprise one or more resources.
 3. The system of claim 1, furthercomprises retaining concurrent support for the first interfaceapplication and the second interface application.
 4. The system of claim1, wherein the changing implementation from the first interfaceapplication to the second interface application comprises temporarilydisabling the first interface application.
 5. The system of claim 1,further comprises identifying differences between the first interfaceapplication and the second interface application.
 6. The system of claim1, wherein the second interface application is a revision of the firstinterface application, and wherein the defined event is an indicationthat a test of the second interface application is complete.
 7. Thesystem of claim 1, wherein the changing implementation comprisesperforming a test of the second interface application during runtime ofthe industrial automation environment.
 8. The system of claim 1, furthercomprises receiving an indication that the second interface applicationis to be deployed within the industrial automation environment, beforethe changing implementation from the first interface application to thesecond interface application.
 9. A computer-implemented method,comprising: using at least one microprocessor, communicatively coupledto at least one memory, to perform the following acts: enabling at leastone of a first interface application and a second interface applicationin an industrial control system, wherein the second interfaceapplication is an updated version of the first interface application;associating a third interface application with the second interfaceapplication or the first interface application based on respective dataassociated with the first interface application, the second interfaceapplication, and the third interface application; enabling the thirdinterface application during runtime; and maintaining concurrent supportof the first interface application, the second interface application,and the third interface application.
 10. The computer-implemented methodof claim 9, wherein the associating the third interface applicationcomprises determining the third interface application is compatible withthe first interface application or the second interface application. 11.The computer-implemented method of claim 9, further comprising:disabling the third interface application based on an occurrence of adefined event; and resuming operation with the first interfaceapplication or the second interface application.
 12. Thecomputer-implemented method of claim 9, further comprises retaininginformation related to a first service of the first interfaceapplication, a second service of the second interface application, and athird service of the third interface application, wherein the firstservice, the second service, and the third service comprise respectivereusable definitions and respective specifications comprising one ormore resources.
 13. A device, comprising: a deployment component thatenables a first platform configuration; and a validation component thatcompares the first platform configuration with a second platformconfiguration and a third platform configuration, wherein the first,second, and third platform configurations are selected from a set ofalternative platform configurations, and wherein the deploymentcomponent enables one of the second platform configuration or the thirdplatform configuration, while maintaining support for the first, second,and third platform configurations.
 14. The device of claim 13, furthercomprising a mapping component that translates information between thefirst platform configuration, the second platform configuration, and thethird platform configuration.
 15. The device of claim 13, wherein thedeployment component is functionally independent of the set ofalternative platform configurations.
 16. The device of claim 13, whereinthe deployment component is configured to be used on at least twoplatform configurations of the set of alternative platformconfigurations, wherein the at least two platform configurations arefunctional equivalents with at least one underlying difference.
 17. Thedevice of claim 13, wherein each platform configuration of the set ofalternative platform configurations comprises a respective service thatis decoupled from another platform configuration of an industrialautomation system.
 18. The device of claim 13, wherein each respectiveservice comprises a reusable definition, a specification, or both thereusable definition and the specification.
 19. The device of claim 13,wherein the deployment component disables the second platformconfiguration or the third platform configuration and resumes operationwith the first platform configuration.
 20. The device of claim 13,wherein the validation component performs a compatibility check of eachplatform configuration in the set of alternative platform configurationsand chooses the second platform configuration or the third platformconfiguration based on a determination that the second platformconfiguration or the third platform configuration is an updated versionof the first platform configuration.